Dynomotion

Group: DynoMotion Message: 7132 From: az9633@ymail.com Date: 3/28/2013
Subject: Program skips commands?
I'm having trouble understanding why this program skips through without waiting for the inputs to activate/deactivate.
The output commands activate the lamp as programmed but the "while" command lines act as if they are'nt even there.

I can see the inputs on the I/O screen and they change as I switch the switches. while this program is running they show as
"off" ("not checked" status)
When watching the console while this progam runs it looks like all console print commands go out all at the same time at the end instead of going out as they execute.

Any suggestions?

AZ



#include "KMotionDef.h"

void main()
{
// int i;
// for (i=0; i<10; i++)
// Punch
{
ClearBit(89);
ClearBit(90);
ClearBit(92);

Delay_sec(2);
SetBit(92);
printf("waiting for Punch go"); // send message to console
Delay_sec(2);
while (ReadBit(48)); //wait for Punch Go Sw
ClearBit(92);
Delay_sec(01);
printf("waiting for Punch run"); // send message to console
while (ReadBit(49)); //wait for Punch run Sw
SetBit(92);

printf("waiting for Tool PB"); // send message to console
Delay_sec(2);
while (ReadBit(50)); //wait for Tool Sw
ClearBit(92);
Delay_sec(0.5);



Delay_sec(0.2);
printf("Flash Tool light once"); // send message to console


SetBit(92);
Delay_sec(1.3);
ClearBit(92);
// Delay_sec(0.3);
// SetBit(92);
// Delay_sec(0.3);
// ClearBit(92);
// Delay_sec(0.3);
// SetBit(92);
// Delay_sec(0.3);
// ClearBit(92);
// Delay_sec(0.3);
// SetBit(92);
// Delay_sec(0.3);
// ClearBit(92);
// Delay_sec(0.3);
// SetBit(92);
// Delay_sec(0.3);
// ClearBit(92);


printf("Punch done\n"); // send message to console

}
}
Group: DynoMotion Message: 7133 From: TK Date: 3/28/2013
Subject: Re: Program skips commands?
Hi AZ,

A new line (line feed) character is required to print the characters. Add a \n to the end of each message like shown in all the examples. 

TK

On Mar 28, 2013, at 6:17 AM, "az9633@..." <az@...> wrote:

 

I'm having trouble understanding why this program skips through without waiting for the inputs to activate/deactivate.
The output commands activate the lamp as programmed but the "while" command lines act as if they are'nt even there.

I can see the inputs on the I/O screen and they change as I switch the switches. while this program is running they show as
"off" ("not checked" status)
When watching the console while this progam runs it looks like all console print commands go out all at the same time at the end instead of going out as they execute.

Any suggestions?

AZ

#include "KMotionDef.h"

void main()
{
// int i;
// for (i=0; i<10; i++)
// Punch
{
ClearBit(89);
ClearBit(90);
ClearBit(92);

Delay_sec(2);
SetBit(92);
printf("waiting for Punch go"); // send message to console
Delay_sec(2);
while (ReadBit(48)); //wait for Punch Go Sw
ClearBit(92);
Delay_sec(01);
printf("waiting for Punch run"); // send message to console
while (ReadBit(49)); //wait for Punch run Sw
SetBit(92);

printf("waiting for Tool PB"); // send message to console
Delay_sec(2);
while (ReadBit(50)); //wait for Tool Sw
ClearBit(92);
Delay_sec(0.5);


Delay_sec(0.2);
printf("Flash Tool light once"); // send message to console


SetBit(92);
Delay_sec(1.3);
ClearBit(92);
// Delay_sec(0.3);
// SetBit(92);
// Delay_sec(0.3);
// ClearBit(92);
// Delay_sec(0.3);
// SetBit(92);
// Delay_sec(0.3);
// ClearBit(92);
// Delay_sec(0.3);
// SetBit(92);
// Delay_sec(0.3);
// ClearBit(92);
// Delay_sec(0.3);
// SetBit(92);
// Delay_sec(0.3);
// ClearBit(92);


printf("Punch done\n"); // send message to console

}
}
Group: DynoMotion Message: 7134 From: himykabibble Date: 3/28/2013
Subject: Re: Program skips commands?
"while this program is running they show as "off" ("not checked" status)" - It sounds like the inputs are normally low, and go high when the switches are pressed? But your while statements wait only when the inputs are high. Perhaps what you need is:

while (!ReadBit(xx));

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, "az9633@..." <az@...> wrote:
>
> I'm having trouble understanding why this program skips through without waiting for the inputs to activate/deactivate.
> The output commands activate the lamp as programmed but the "while" command lines act as if they are'nt even there.
>
> I can see the inputs on the I/O screen and they change as I switch the switches. while this program is running they show as
> "off" ("not checked" status)
> When watching the console while this progam runs it looks like all console print commands go out all at the same time at the end instead of going out as they execute.
>
> Any suggestions?
>
> AZ
>
>
>
> #include "KMotionDef.h"
>
> void main()
> {
> // int i;
> // for (i=0; i<10; i++)
> // Punch
> {
> ClearBit(89);
> ClearBit(90);
> ClearBit(92);
>
> Delay_sec(2);
> SetBit(92);
> printf("waiting for Punch go"); // send message to console
> Delay_sec(2);
> while (ReadBit(48)); //wait for Punch Go Sw
> ClearBit(92);
> Delay_sec(01);
> printf("waiting for Punch run"); // send message to console
> while (ReadBit(49)); //wait for Punch run Sw
> SetBit(92);
>
> printf("waiting for Tool PB"); // send message to console
> Delay_sec(2);
> while (ReadBit(50)); //wait for Tool Sw
> ClearBit(92);
> Delay_sec(0.5);
>
>
>
> Delay_sec(0.2);
> printf("Flash Tool light once"); // send message to console
>
>
> SetBit(92);
> Delay_sec(1.3);
> ClearBit(92);
> // Delay_sec(0.3);
> // SetBit(92);
> // Delay_sec(0.3);
> // ClearBit(92);
> // Delay_sec(0.3);
> // SetBit(92);
> // Delay_sec(0.3);
> // ClearBit(92);
> // Delay_sec(0.3);
> // SetBit(92);
> // Delay_sec(0.3);
> // ClearBit(92);
> // Delay_sec(0.3);
> // SetBit(92);
> // Delay_sec(0.3);
> // ClearBit(92);
>
>
> printf("Punch done\n"); // send message to console
>
> }
> }
>
Group: DynoMotion Message: 7139 From: az9633@ymail.com Date: 3/29/2013
Subject: Re: Program skips commands?
You are right about the status of the inputs and changing the while statements as you described but I still have the same problem but only when I use the Inputs.

When I use the intermal bits and trigger them by changing their states on the I/O monitor window the program runs as designed. I must have some noise issues but I NEVER see the Inputs showing as On, even for a flash, while viewing the I/O window when it's not activated. I realize the PC I/O window isn't real time but I would expect that it would occasionally catch the input on due to noise but it doesn't seem to.

I'm using a SnapAmp and I'm using the internal opto inputs as well as the LVTTL inputs isolated via external optos. The inputs that are having a problem are the ones with the external optos. I'm pulling the LVTTL inptus down to the K flop 5V common with 1K resistors and activating them with 3 v regulated down from the K flop 5 Volt supply from the Ribbon cable connector. The 5 volt K flop power supply is floating (not grounded) and the 24 V Machine I/O supply on the other side of the Optos is grounded.

I'm going to try the internal optos and will try disabling the SnapAmp to see if that's where the noise is coming from.

AZ

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy1964@...> wrote:
>
> "while this program is running they show as "off" ("not checked" status)" - It sounds like the inputs are normally low, and go high when the switches are pressed? But your while statements wait only when the inputs are high. Perhaps what you need is:
>
> while (!ReadBit(xx));
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "az9633@" <az@> wrote:
> >
> > I'm having trouble understanding why this program skips through without waiting for the inputs to activate/deactivate.
> > The output commands activate the lamp as programmed but the "while" command lines act as if they are'nt even there.
> >
> > I can see the inputs on the I/O screen and they change as I switch the switches. while this program is running they show as
> > "off" ("not checked" status)
> > When watching the console while this progam runs it looks like all console print commands go out all at the same time at the end instead of going out as they execute.
> >
> > Any suggestions?
> >
> > AZ
> >
> >
> >
> > #include "KMotionDef.h"
> >
> > void main()
> > {
> > // int i;
> > // for (i=0; i<10; i++)
> > // Punch
> > {
> > ClearBit(89);
> > ClearBit(90);
> > ClearBit(92);
> >
> > Delay_sec(2);
> > SetBit(92);
> > printf("waiting for Punch go"); // send message to console
> > Delay_sec(2);
> > while (ReadBit(48)); //wait for Punch Go Sw
> > ClearBit(92);
> > Delay_sec(01);
> > printf("waiting for Punch run"); // send message to console
> > while (ReadBit(49)); //wait for Punch run Sw
> > SetBit(92);
> >
> > printf("waiting for Tool PB"); // send message to console
> > Delay_sec(2);
> > while (ReadBit(50)); //wait for Tool Sw
> > ClearBit(92);
> > Delay_sec(0.5);
> >
> >
> >
> > Delay_sec(0.2);
> > printf("Flash Tool light once"); // send message to console
> >
> >
> > SetBit(92);
> > Delay_sec(1.3);
> > ClearBit(92);
> > // Delay_sec(0.3);
> > // SetBit(92);
> > // Delay_sec(0.3);
> > // ClearBit(92);
> > // Delay_sec(0.3);
> > // SetBit(92);
> > // Delay_sec(0.3);
> > // ClearBit(92);
> > // Delay_sec(0.3);
> > // SetBit(92);
> > // Delay_sec(0.3);
> > // ClearBit(92);
> > // Delay_sec(0.3);
> > // SetBit(92);
> > // Delay_sec(0.3);
> > // ClearBit(92);
> >
> >
> > printf("Punch done\n"); // send message to console
> >
> > }
> > }
> >
>
Group: DynoMotion Message: 7231 From: az9633@ymail.com Date: 4/10/2013
Subject: Re: Program skips commands?
I found that the C code I/O program worked properly if I disabled the Snap Amp by forcing a fault caused by setting the peak current to 5.

I was able to see the Snap Amp PWM switching noise on the K flop side of my opto isolator.


I did a couple of things to improve this but it seems that the most effective change was connecting a wire from the Kflop PCB ground point ( 5v common) to the I/O isolator board. Previiuosly when I was having trouble I was using only the 5v and 0v from the ribbon cable breakout module.

My I/O layout is like this:
Kflop to 50 pin breakout board at the end of a 12 inch ribbon cable.

AZ


--- In DynoMotion@yahoogroups.com, "az9633@..." <az@...> wrote:
>
> You are right about the status of the inputs and changing the while statements as you described but I still have the same problem but only when I use the Inputs.
>
> When I use the intermal bits and trigger them by changing their states on the I/O monitor window the program runs as designed. I must have some noise issues but I NEVER see the Inputs showing as On, even for a flash, while viewing the I/O window when it's not activated. I realize the PC I/O window isn't real time but I would expect that it would occasionally catch the input on due to noise but it doesn't seem to.
>
> I'm using a SnapAmp and I'm using the internal opto inputs as well as the LVTTL inputs isolated via external optos. The inputs that are having a problem are the ones with the external optos. I'm pulling the LVTTL inptus down to the K flop 5V common with 1K resistors and activating them with 3 v regulated down from the K flop 5 Volt supply from the Ribbon cable connector. The 5 volt K flop power supply is floating (not grounded) and the 24 V Machine I/O supply on the other side of the Optos is grounded.
>
> I'm going to try the internal optos and will try disabling the SnapAmp to see if that's where the noise is coming from.
>
> AZ
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy1964@> wrote:
> >
> > "while this program is running they show as "off" ("not checked" status)" - It sounds like the inputs are normally low, and go high when the switches are pressed? But your while statements wait only when the inputs are high. Perhaps what you need is:
> >
> > while (!ReadBit(xx));
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, "az9633@" <az@> wrote:
> > >
> > > I'm having trouble understanding why this program skips through without waiting for the inputs to activate/deactivate.
> > > The output commands activate the lamp as programmed but the "while" command lines act as if they are'nt even there.
> > >
> > > I can see the inputs on the I/O screen and they change as I switch the switches. while this program is running they show as
> > > "off" ("not checked" status)
> > > When watching the console while this progam runs it looks like all console print commands go out all at the same time at the end instead of going out as they execute.
> > >
> > > Any suggestions?
> > >
> > > AZ
> > >
> > >
> > >
> > > #include "KMotionDef.h"
> > >
> > > void main()
> > > {
> > > // int i;
> > > // for (i=0; i<10; i++)
> > > // Punch
> > > {
> > > ClearBit(89);
> > > ClearBit(90);
> > > ClearBit(92);
> > >
> > > Delay_sec(2);
> > > SetBit(92);
> > > printf("waiting for Punch go"); // send message to console
> > > Delay_sec(2);
> > > while (ReadBit(48)); //wait for Punch Go Sw
> > > ClearBit(92);
> > > Delay_sec(01);
> > > printf("waiting for Punch run"); // send message to console
> > > while (ReadBit(49)); //wait for Punch run Sw
> > > SetBit(92);
> > >
> > > printf("waiting for Tool PB"); // send message to console
> > > Delay_sec(2);
> > > while (ReadBit(50)); //wait for Tool Sw
> > > ClearBit(92);
> > > Delay_sec(0.5);
> > >
> > >
> > >
> > > Delay_sec(0.2);
> > > printf("Flash Tool light once"); // send message to console
> > >
> > >
> > > SetBit(92);
> > > Delay_sec(1.3);
> > > ClearBit(92);
> > > // Delay_sec(0.3);
> > > // SetBit(92);
> > > // Delay_sec(0.3);
> > > // ClearBit(92);
> > > // Delay_sec(0.3);
> > > // SetBit(92);
> > > // Delay_sec(0.3);
> > > // ClearBit(92);
> > > // Delay_sec(0.3);
> > > // SetBit(92);
> > > // Delay_sec(0.3);
> > > // ClearBit(92);
> > > // Delay_sec(0.3);
> > > // SetBit(92);
> > > // Delay_sec(0.3);
> > > // ClearBit(92);
> > >
> > >
> > > printf("Punch done\n"); // send message to console
> > >
> > > }
> > > }
> > >
> >
>